build(deps-dev): bump the testing group across 1 directory with 3 updates by dependabot[bot] · Pull Request #384 · julianken/detached-node

dependabot · 2026-05-15T00:56:27Z

Bumps the testing group with 3 updates in the / directory: @playwright/test, @vitest/coverage-v8 and vitest.

Updates @playwright/test from 1.59.1 to 1.60.0

Release notes

Sourced from @playwright/test's releases.

v1.60.0

🌐 HAR recording on Tracing

tracing.startHar() / tracing.stopHar() expose HAR recording as a first-class tracing API, with the same content, mode and urlFilter options as recordHar. The returned Disposable makes it easy to scope a recording with await using:
await using har = await context.tracing.startHar('trace.har');
const page = await context.newPage();
await page.goto('https://playwright.dev');
// HAR is finalized when `har` goes out of scope.
🪝 Drop API

New locator.drop() simulates an external drag-and-drop of files or clipboard-like data onto an element. Playwright dispatches dragenter, dragover, and drop with a synthetic [DataTransfer] in the page context — works cross-browser and is great for testing upload zones:
await page.locator('#dropzone').drop({
  files: { name: 'note.txt', mimeType: 'text/plain', buffer: Buffer.from('hello') },
});
await page.locator('#dropzone').drop({
data: {
'text/plain': 'hello world',
'text/uri-list': 'https://example.com',
},
});
🎯 Aria snapshots

expect(page).toMatchAriaSnapshot() now works on a Page, in addition to a Locator — equivalent to asserting against page.locator('body').

New boxes option on locator.ariaSnapshot() / page.ariaSnapshot() appends each element's bounding box as [box=x,y,width,height], useful for AI consumption.

🛑 test.abort()

New test.abort() aborts the currently running test from a fixture, hook, or route handler with an optional message. Use it when you have detected an unrecoverable misuse and want to fail the test right away:
test('does not publish to the shared page', async ({ page }) => {
  await page.route('**/publish', route => {
    test.abort('Tests must not publish to the shared page. Use the `clone` option.');
    return route.abort();
  });
  // ...
});
New APIs

Browser, Context and Page

... (truncated)

Commits

87bb9dd cherry-pick(#40747): fix(yauzl): vendor yauzl with destroy-lifecycle fix
9a9c51c cherry-pick(#40733): chore(electron): revert #40184 (move Electron API to a s...
4b3b628 cherry-pick(#40736): Revert "feat(electron): add timeout option to electronAp...
f869f96 chore: bump version to v1.60.0 (#40714)
7eb6918 cherry-pick(#40710): docs: release notes v1.60
118d2aa cherry-pick(#40693): chore(python): formdata path type
54012f5 chore(deps): bump ip-address and express-rate-limit (#40680)
9fa531d fix(screencast): unblock frame ack when an async client disconnects (#40674)
3649db5 chore(mcp): bump default extension protocol to v2 (#40678)
bb6c009 chore(extension): mark 0.2.1 (#40679)
Additional commits viewable in compare view

Updates @vitest/coverage-v8 from 4.1.4 to 4.1.6

Release notes

Sourced from @vitest/coverage-v8's releases.

v4.1.6

   🐞 Bug Fixes

browser: Provide project reference in ToMatchScreenshotResolvePath - by @macarie and @sheremet-va in vitest-dev/vitest#10138 (31882)

Global sequence.concurrent: true with top-level test(..., { concurrent: false }) + depreacte sequential test API and options - by @hi-ogawa, Codex and @sheremet-va in vitest-dev/vitest#10196 (2847d)

browser: Simplify orchestrator otel carrier - by @hi-ogawa in vitest-dev/vitest#10285 (18af9)

   🏎 Performance

Stringify diff objects only once - by @sheremet-va in vitest-dev/vitest#10276 (9f7b1)

    View changes on GitHub

v4.1.5

   🚀 Experimental Features

coverage: Istanbul to support instrumenter option - by @BartWaardenburg and @AriPerkkio in vitest-dev/vitest#10119 (0e0ff)

   🐞 Bug Fixes

--project negation excludes browser instances - by @felamaslen in vitest-dev/vitest#10131 (9423d)

Project color label on html reporter - by @hi-ogawa in vitest-dev/vitest#10142 (596f7)

Fix vi.defineHelper called as object method - by @hi-ogawa in vitest-dev/vitest#10163 (122c2)

Alias agent reporter to minimal - by @sheremet-va in vitest-dev/vitest#10157 (663b9)

Respect diff config options in soft assertions - by @Copilot, sheremet-va and @sheremet-va in vitest-dev/vitest#8696 (9787d)

Respect diff config options in soft assertions " - by @sheremet-va in vitest-dev/vitest#8696 (7dc6d)

ast-collect: Recognize _vi_import prefix in static test discovery - by @Yejneshwar in vitest-dev/vitest#10129 (32546)

coverage: Descriptive error message when reports directory is removed during test run - by @DaveT1991 and @AriPerkkio in vitest-dev/vitest#10117 (14133)

snapshot: Increase default snapshot max output length - by @hi-ogawa and Codex in vitest-dev/vitest#10150 (21e66)

ui: Fix jsx/tsx syntax highlight - by @hi-ogawa in vitest-dev/vitest#10152 (f1b1f)

web-worker: Support MessagePort objects referenced inside postMessage data - by @whitphx and Claude Opus 4.6 (1M context) in vitest-dev/vitest#9927 and vitest-dev/vitest#10124 (7ad7d)

api: Make test-specification options writable - by @sheremet-va in vitest-dev/vitest#10154 (6abd5)

    View changes on GitHub

Commits

a8fd24c chore: release v4.1.6
e399846 chore: release v4.1.5
See full diff in compare view

Updates vitest from 4.1.4 to 4.1.6

Release notes

Sourced from vitest's releases.

v4.1.6

   🐞 Bug Fixes

browser: Provide project reference in ToMatchScreenshotResolvePath - by @macarie and @sheremet-va in vitest-dev/vitest#10138 (31882)

Global sequence.concurrent: true with top-level test(..., { concurrent: false }) + depreacte sequential test API and options - by @hi-ogawa, Codex and @sheremet-va in vitest-dev/vitest#10196 (2847d)

browser: Simplify orchestrator otel carrier - by @hi-ogawa in vitest-dev/vitest#10285 (18af9)

   🏎 Performance

Stringify diff objects only once - by @sheremet-va in vitest-dev/vitest#10276 (9f7b1)

    View changes on GitHub

v4.1.5

   🚀 Experimental Features

coverage: Istanbul to support instrumenter option - by @BartWaardenburg and @AriPerkkio in vitest-dev/vitest#10119 (0e0ff)

   🐞 Bug Fixes

--project negation excludes browser instances - by @felamaslen in vitest-dev/vitest#10131 (9423d)

Project color label on html reporter - by @hi-ogawa in vitest-dev/vitest#10142 (596f7)

Fix vi.defineHelper called as object method - by @hi-ogawa in vitest-dev/vitest#10163 (122c2)

Alias agent reporter to minimal - by @sheremet-va in vitest-dev/vitest#10157 (663b9)

Respect diff config options in soft assertions - by @Copilot, sheremet-va and @sheremet-va in vitest-dev/vitest#8696 (9787d)

Respect diff config options in soft assertions " - by @sheremet-va in vitest-dev/vitest#8696 (7dc6d)

ast-collect: Recognize _vi_import prefix in static test discovery - by @Yejneshwar in vitest-dev/vitest#10129 (32546)

coverage: Descriptive error message when reports directory is removed during test run - by @DaveT1991 and @AriPerkkio in vitest-dev/vitest#10117 (14133)

snapshot: Increase default snapshot max output length - by @hi-ogawa and Codex in vitest-dev/vitest#10150 (21e66)

ui: Fix jsx/tsx syntax highlight - by @hi-ogawa in vitest-dev/vitest#10152 (f1b1f)

web-worker: Support MessagePort objects referenced inside postMessage data - by @whitphx and Claude Opus 4.6 (1M context) in vitest-dev/vitest#9927 and vitest-dev/vitest#10124 (7ad7d)

api: Make test-specification options writable - by @sheremet-va in vitest-dev/vitest#10154 (6abd5)

    View changes on GitHub

Commits

a8fd24c chore: release v4.1.6
18af98c fix(browser): simplify orchestrator otel carrier (#10285)
3188260 feat(browser): provide project reference in ToMatchScreenshotResolvePath (#...
e399846 chore: release v4.1.5
7dc6d54 Revert "fix: respect diff config options in soft assertions (#8696)"
9787ded fix: respect diff config options in soft assertions (#8696)
325463a fix(ast-collect): recognize _vi_import prefix in static test discovery (#10...
0e0ff41 feat(coverage): istanbul to support instrumenter option (#10119)
663b99f fix: alias agent reporter to minimal (#10157)
122c25b fix: fix vi.defineHelper called as object method (#10163)
Additional commits viewable in compare view

julianken-bot · 2026-05-18T00:54:31Z

@dependabot rebase

julianken-bot · 2026-05-18T01:00:02Z

@dependabot recreate

…ates Bumps the testing group with 3 updates in the / directory: [@playwright/test](https://github.com/microsoft/playwright), [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@playwright/test` from 1.59.1 to 1.60.0 - [Release notes](https://github.com/microsoft/playwright/releases) - [Commits](microsoft/playwright@v1.59.1...v1.60.0) Updates `@vitest/coverage-v8` from 4.1.4 to 4.1.6 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.6/packages/coverage-v8) Updates `vitest` from 4.1.4 to 4.1.6 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.6/packages/vitest) --- updated-dependencies: - dependency-name: "@playwright/test" dependency-version: 1.60.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: testing - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.6 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: testing - dependency-name: vitest dependency-version: 4.1.6 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: testing ... Signed-off-by: dependabot[bot] <support@github.com>

julianken-bot

Verdict: APPROVE

Verification ledger

gh pr view 384 — HEAD d1ad157 on dependabot/npm_and_yarn/testing-3926fea3e4, base fe7d830, mergeable, not draft.
gh pr diff 384 — 2 files: package.json (3 minor version bumps, dev-only), pnpm-lock.yaml (regenerated graph).
git log fe7d830..d1ad157 — 2 commits: Dependabot bump 216ea24, then Julian's lockfile fix d1ad157.
git show d1ad157 — fix touches 3 lines of pnpm-lock.yaml only; replaces sha256-hex patch_hash (Dependabot's pnpm 10+ output, 96ac089b...64chars) with base32 short hash nxvyby6r4isjnouuw656h2bwdi matching main and pnpm 9's hash format.
git diff fe7d830..d1ad157 -- patches/ — empty (patch file content unchanged, only the lockfile reference to it).
git show fe7d830:pnpm-lock.yaml | grep patch_hash — confirms main already uses base32 nxvyby6r4isjnouuw656h2bwdi (same value on disk now), so the fix restores byte-for-byte the same hash format CI expects.
pnpm --version → 9.15.9 locally; Dockerfile line 2 pins corepack prepare pnpm@9 --activate — runtime and lockfile format match.
gh pr view 384 --json statusCheckRollup — all 12 required checks SUCCESS (ESLint, TypeScript, Vitest, Next.js Build, Analyze Bundle, CodeQL, E2E Shards 1/4–4/4); CodeQL Analysis SUCCESS; Mergify queue NEUTRAL (expected, not yet queued).

Findings ToC

SUGGESTION: pin packageManager in package.json to prevent recurring Dependabot lockfile-format drift (followup, out of scope for this PR)

What's specifically right

The fix was scoped surgically: 3 lines of lockfile, no spec change, no package.json touch, no pnpm version change. That's the minimum diff that resolves the CI failure.
The chosen resolution path (local pnpm 9 regeneration) is the correct one — @dependabot recreate produced the wrong format because Dependabot's environment uses pnpm 10, and there is no way to override that from within a PR. Recognizing this and bypassing the recreate loop saved an iteration.
The patch file patches/next-view-transitions.patch itself was not modified — confirms the underlying patched dependency content is unchanged; only the hash representation differs between pnpm versions, not the patch content.

Bottom line

Single-commit fix on top of a clean Dependabot devDependency bump (3 testing packages, all minor). CI fully green on the post-fix HEAD. Safe to queue.

— @julianken-bot (opus, fresh context)

julianken-bot · 2026-05-18T01:44:52Z

@@ -49,7 +49,7 @@
  "devDependencies": {
    "@ai-sdk/openai": "^1",


SUGGESTION — followup, not blocking this PR.

This same CI failure will recur on every Dependabot dev-deps PR as long as Dependabot's bot environment uses a different pnpm major than main's lockfile. Each future Dependabot PR will regenerate patch_hash here in pnpm 10's sha256-hex format and break --frozen-lockfile.

Structural fix (separate followup PR): add a packageManager: "pnpm@9.15.9" field to package.json. Once that's present, corepack will force Dependabot's own CI to use pnpm 9 when it runs pnpm install on the bumped branch, so the regenerated hash will already be in the base32 format matching main and the Dockerfile — no Julian-side manual regeneration needed.

R9 note: this is plan-controlled (a repo-level Dependabot/toolchain decision), not implementer-controlled for this PR. Filing here as a SUGGESTION because the friction is recurring and the fix is mechanical (one line + a Dependabot config update).

julianken-bot · 2026-05-18T01:53:04Z

@Mergifyio queue

mergify · 2026-05-18T01:53:28Z

Merge Queue Status

🛑 Queue command has been cancelled

# Conflicts: # pnpm-lock.yaml

julianken-bot

Verdict: APPROVE (re-review after rebase + lockfile regen)

Verification ledger

gh pr view 384 — HEAD 36dbff2 on dependabot/npm_and_yarn/testing-3926fea3e4, base 65febfb, mergeable, not draft. Prior bot APPROVE on d1ad157 was dismissed when the merge commit landed (branch-protection behavior, expected).
git log fe7d830..36dbff2 — branch history: 216ea24 Dependabot bump → d1ad157 Julian lockfile fix (pnpm 9 base32 hash) → 36dbff2 merge of origin/main (carrying #372 graphql + #222 jsdom). Merge author Julian via noreply email; conflict in pnpm-lock.yaml only, as stated.
git diff origin/main..36dbff2 --stat — 2 files: package.json (+3/-3) and pnpm-lock.yaml (+131/-129). Diff vs current main matches the dispatcher's claim exactly: testing-group package.json bumps + reconciled lockfile.
git diff origin/main..36dbff2 -- package.json — exactly 3 specifier bumps: @playwright/test ^1.59.1→^1.60.0, @vitest/coverage-v8 ^4.1.4→^4.1.6, vitest ^4.1.4→^4.1.6. No additions or removals.
Lockfile transitives audit — playwright/playwright-core 1.59→1.60 (direct), plus vitest 4.1.6's closure: magicast 0.5.2→0.5.3, tinyexec 1.0.2→1.1.2, es-module-lexer 2.0.0→2.1.0, semver 7.7.4→7.8.0, @babel/parser@7.29.3 added, @types/estree@1.0.9 added, picomatch@4.0.3 removed (4.0.4 retained), tinyglobby@0.2.15 removed (0.2.16 retained). All consistent with the testing-group bumps; no unrelated package movement, no resurrection of graphql@16.13.2 or jsdom@29.0.2 (proves clean merge with the freshly-landed #372 / #222).
git diff origin/main..36dbff2 -- patches/ — empty. patches/next-view-transitions.patch untouched.
patch_hash check — git show origin/main:pnpm-lock.yaml | grep patch_hash and git show 36dbff2:pnpm-lock.yaml | grep patch_hash both show patch_hash=nxvyby6r4isjnouuw656h2bwdi (pnpm 9 base32 format). The CI hash-format regression that motivated the rebase is resolved.
pnpm --version locally → 9.15.9; Dockerfile pins corepack prepare pnpm@9 --activate. Runtime and lockfile format agree.
gh pr checks 384 — all 12 required checks SUCCESS on 36dbff2: ESLint, TypeScript, Vitest, Next.js Build, Analyze Bundle, CodeQL, CodeQL Analysis, E2E Shards 1/4–4/4. Mergify queue NEUTRAL (expected; not yet queued).
gh api .../collaborators/julianken-bot/permission → write (APPROVE event valid).

Findings ToC

SUGGESTION: pin packageManager: "pnpm@9.15.9" in package.json — would prevent the pnpm 9 vs 10 lockfile-format drift that caused this whole rebase round. Follow-up, out of scope here.

What's specifically right

The merge commit is a true rebase-via-merge: only conflict was pnpm-lock.yaml, and the regenerated lockfile reconciles cleanly with both the upstream graphql/jsdom bumps and the local testing-group bump. No "let's also touch unrelated config while we're here" drift.
The patch_hash format (nxvyby6r4isjnouuw656h2bwdi, base32) is byte-identical to main. This is the load-bearing detail — it's why CI flipped from red on Dependabot's sha256-hex regenerate to green here.
Diff vs current main is exactly the two files the dispatch claimed. The merge commit's mechanical 4-file diff (which includes workflow files brought in from main) reconciles to a 2-file delta against main. Verified independently from the diff command, not trusted from narrative.

Bottom line

Same content as the prior APPROVE (d1ad157), now rebased atop a moved main with the lockfile re-reconciled. CI fully green on the post-rebase HEAD. Safe to queue.

— @julianken-bot (opus, fresh context)

julianken-bot · 2026-05-18T02:15:33Z

@Mergifyio queue

mergify · 2026-05-18T02:17:38Z

# Conflicts: # pnpm-lock.yaml

julianken-bot

Verdict: APPROVE — second rebase reconciles cleanly; diff vs main is still just the testing-group bump and a regenerated lockfile, and all checks I ran locally pass.

What I verified (this turn)

git diff origin/main..pr-384 -- package.json → only the three intended specifier bumps (@playwright/test 1.59.1→1.60.0, @vitest/coverage-v8 and vitest 4.1.4→4.1.6); no other devDependency or pnpm.patchedDependencies lines touched.
git diff origin/main..pr-384 --stat → 2 files (package.json, pnpm-lock.yaml); 17 lockfile entries added, 17 removed (clean swap, no orphans). All added entries are within the testing-group transitive closure (@playwright/*, playwright-core, @vitest/* cluster, magicast@0.5.3, @babel/parser@7.29.3, es-module-lexer@2.1.0, semver@7.8.0, tinyexec@1.1.2) — verified magicast@0.5.3 pulls @babel/parser@7.29.3 per its lockfile dependencies block.
git log 5cf65e9e ^36dbff2092 → the new merge commit is solely the origin/main integration (brings in #129 payload + #131 tailwind from the now-merged ahead-of-#384 work); authored by Julian <14049295+julianken@users.noreply.github.com> as expected.
pnpm install --frozen-lockfile --prefer-offline (in a /tmp worktree at head 5cf65e9e) → resolves cleanly with @playwright/test 1.60.0, @vitest/coverage-v8 4.1.6, vitest 4.1.6 (Done in 6.7s); patch hash nxvyby6r4isjnouuw656h2bwdi for next-view-transitions unchanged, so #383's pnpm patch is still applied.
pnpm exec vitest run → Test Files 37 passed (37) / Tests 584 passed (584) / Duration 6.54s on vitest 4.1.6.
pnpm exec tsc --noEmit → 0 errors. pnpm exec eslint . → 0 errors, 18 pre-existing warnings unrelated to this PR.
gh api repos/julianken/detached-node/collaborators/julianken-bot/permission → write (APPROVE event will land).

Findings (0 — see inline comments below for detail)

None. Mandatory second-pass read surfaced no real issues. The merge commit is a pure conflict-resolution-by-regeneration of the lockfile; the package.json delta vs main is exactly the three Dependabot-intended specifier bumps; the @babel/parser / magicast / es-module-lexer transitive shuffle is internally consistent with the vitest cluster moving 4.1.4→4.1.6; the pnpm.patchedDependencies config and patch hash are preserved.

Bottom line: ready to merge. Note that #369 (next-react group) and #314 (ai-sdk group) remain open — whichever of those merges next will displace this PR's lockfile state again, so prefer to queue this PR sooner rather than later.

Reviewer: @julianken-bot (opus) — fresh-context subagent dispatched via the reviewing-as-julianken-bot skill. Verdict above is binding regardless of GitHub's review label.

julianken-bot · 2026-05-18T02:29:38Z

@Mergifyio queue

mergify · 2026-05-18T02:29:52Z

queue

☑️ Command `queue` ignored because it is already running from a previous command.

mergify · 2026-05-18T02:30:38Z

dependabot Bot added the dependencies Pull requests that update a dependency file label May 15, 2026

dependabot Bot changed the title ~~build(deps-dev): bump the testing group across 1 directory with 3 updates~~ chore(deps-dev): bump the testing group across 1 directory with 3 updates May 18, 2026

dependabot Bot force-pushed the dependabot/npm_and_yarn/testing-3926fea3e4 branch from 73e23a5 to dfae92e Compare May 18, 2026 00:57

dependabot Bot force-pushed the dependabot/npm_and_yarn/testing-3926fea3e4 branch from dfae92e to 02ed29a Compare May 18, 2026 01:02

dependabot Bot changed the title ~~chore(deps-dev): bump the testing group across 1 directory with 3 updates~~ build(deps-dev): bump the testing group across 1 directory with 3 updates May 18, 2026

dependabot Bot force-pushed the dependabot/npm_and_yarn/testing-3926fea3e4 branch from 02ed29a to e02dfca Compare May 18, 2026 01:06

dependabot Bot force-pushed the dependabot/npm_and_yarn/testing-3926fea3e4 branch from e02dfca to 216ea24 Compare May 18, 2026 01:09

fix(deps): regenerate lockfile for patchedDependencies hash

d1ad157

julianken-bot previously approved these changes May 18, 2026

View reviewed changes

mergify Bot added queued dequeued and removed queued labels May 18, 2026

Merge remote-tracking branch 'origin/main' into td-384-fix2

36dbff2

# Conflicts: # pnpm-lock.yaml

julianken dismissed julianken-bot’s stale review via 36dbff2 May 18, 2026 02:06

mergify Bot removed the dequeued label May 18, 2026

julianken-bot previously approved these changes May 18, 2026

View reviewed changes

Merge remote-tracking branch 'origin/main' into td-384-fix3

5cf65e9

# Conflicts: # pnpm-lock.yaml

julianken dismissed julianken-bot’s stale review via 5cf65e9 May 18, 2026 02:21

julianken-bot approved these changes May 18, 2026

View reviewed changes

mergify Bot added the queued label May 18, 2026

mergify Bot merged commit ec7099b into main May 18, 2026
13 checks passed

mergify Bot deleted the dependabot/npm_and_yarn/testing-3926fea3e4 branch May 18, 2026 02:31

mergify Bot removed the queued label May 18, 2026

		@@ -49,7 +49,7 @@
		"devDependencies": {
		"@ai-sdk/openai": "^1",

Conversation

dependabot Bot commented on behalf of github May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v1.60.0

🌐 HAR recording on Tracing

🪝 Drop API

🎯 Aria snapshots

🛑 test.abort()

New APIs

Browser, Context and Page

v4.1.6

🐞 Bug Fixes

🏎 Performance

View changes on GitHub

v4.1.5

🚀 Experimental Features

🐞 Bug Fixes

View changes on GitHub

v4.1.6

🐞 Bug Fixes

🏎 Performance

View changes on GitHub

v4.1.5

🚀 Experimental Features

🐞 Bug Fixes

View changes on GitHub

Uh oh!

julianken-bot commented May 18, 2026

Uh oh!

julianken-bot commented May 18, 2026

Uh oh!

julianken-bot left a comment

Choose a reason for hiding this comment

Verification ledger

Findings ToC

What's specifically right

Bottom line

Uh oh!

julianken-bot May 18, 2026

Choose a reason for hiding this comment

Uh oh!

julianken-bot commented May 18, 2026

Uh oh!

mergify Bot commented May 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merge Queue Status

Uh oh!

julianken-bot left a comment

Choose a reason for hiding this comment

Verification ledger

Findings ToC

What's specifically right

Bottom line

Uh oh!

julianken-bot commented May 18, 2026

Uh oh!

mergify Bot commented May 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merge Queue Status

Uh oh!

julianken-bot left a comment

Choose a reason for hiding this comment

What I verified (this turn)

Findings (0 — see inline comments below for detail)

Uh oh!

julianken-bot commented May 18, 2026

Uh oh!

mergify Bot commented May 18, 2026

☑️ Command queue ignored because it is already running from a previous command.

Uh oh!

mergify Bot commented May 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merge Queue Status

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

dependabot Bot commented on behalf of github May 15, 2026 •

edited

Loading

mergify Bot commented May 18, 2026 •

edited

Loading

mergify Bot commented May 18, 2026 •

edited

Loading

☑️ Command `queue` ignored because it is already running from a previous command.

mergify Bot commented May 18, 2026 •

edited

Loading